Systems and methods for managing messages in an enterprise network

ABSTRACT

A protocol management system is capable of detecting certain message protocols and applying policy rules to the detected message protocols that prevent intrusion, or abuse, of a network&#39;s resources. In one aspect, a protocol message gateway is configured to apply policy rules to high level message protocols, such as those that reside at layer 7 of the ISO protocol stack.

RELATED APPLICATIONS INFORMATION

This application claims priority as a continuation application under 35U.S.C. §120 to U.S. patent application Ser. No. 11/869,575, entitled“SYSTEMS AND METHODS FOR REFLECTING MESSAGES ASSOCIATED WITH A TARGETPROTOCOL WITHIN A NETWORK,” filed Oct. 9, 2007, now U.S. Pat. No.7,882,265, issued Feb. 1, 2011, which is a continuation of U.S. patentapplication Ser. No. 10/459,725, entitled “SYSTEMS AND METHODS FORREFLECTING MESSAGES ASSOCIATED WITH A TARGET PROTOCOL WITHIN A NETWORK,”filed on Jun. 10, 2003, now U.S. Pat. No. 7,428,590, issued Sep. 23,2008, which is a continuation-in-part of U.S. application Ser. No.10/167,228, filed Jun. 10, 2002 now abandoned and which also claimspriority under 35 U.S.C. §119 to U.S. Provisional Application No.60/387,761, entitled “PROXY ENFORCER FOR ROGUE PROTOCOL MESSAGES,” filedon Jun. 10, 2002, and to U.S. Provisional Application No. 60/445,648,entitled “DETECTION AND REPORTING OF USER PRESENCE,” filed on Feb. 7,2003. Each of the foregoing applications is hereby incorporated byreference herein as if set forth in its entirety.

BACKGROUND

1. Field of the Inventions

The field of the invention relates generally to digital communicationsnetworks and more particularly to the management of a plurality ofprotocols over such networks including dynamic protocols such as“Instant Message” protocols.

2. Background Information

When a local computing device coupled to a local, or proprietary,network communicates with a remote computing device outside the network,the network can become subject to attempts at intrusion. Intrusion can,for example, be defined as someone trying to wrongfully access thenetwork. Intrusion can also be defined as a program, such as a computervirus, attempting to wrongfully access resources available on thenetwork. For example, a computer virus can be sent from a remotecomputing device to the local computing device, and if allowed tooperate on the local computing device, can commandeer resources at thelocal computing device as well as other local resources, such as thoseavailable to the local computing device on the network or otherwise. Foranother example, a remote computing device can generate a set ofmessages in an attempt to deny service to, or otherwise have an effecton service at, the local computing device, such as preventing access bythat local computing device to proper resources, or by preventing accessby others to that local computing device.

In some cases, intrusion can be caused by messages directed at thenetwork, while in other cases, intrusion can be caused by messages frominside the network, such as from a computing device within the networkunder the control of a computer virus or an employee using the networkimproperly. For example, a computing device within the network can becorrupted by a malicious user of that computing device, i.e., a user whois attempting to access local resources in a way that is not desired. Acomputing device can also be corrupted in a relatively innocent way,such as when a program is otherwise innocently introduced into a devicehaving access to local resources, but where the program itself includesfunctions that attempt to access local resources in a way that is notdesired.

It is therefore sometimes desirable to apply policy rules for handlingmessages in the network, particularly when those messages use a messageprotocol that might not be directed to business aspects of the network.For example, a number of message protocols have been developed recentlythat are primarily for personal use, but which often make their way intoproprietary networks, such as enterprise networks, and which are subjectto possible abuses. These message protocols include, for example,instant message (IM) protocols, peer-to-peer (P2P) and other filesharing protocols, interactive game protocols, distributed computingprotocols, HTTP Tunneling, and “.NET” or “SOAP” methods of computerprogram interaction. Some of the possible abuses that can result fromthese message protocols entering the enterprise network includeaccidental delivery of a computer virus to a client device within theenterprise network, communication of sensitive or proprietaryinformation between client devices within the enterprise network andclient devices outside the enterprise network, and other unauthorizeduser behavior within the enterprise network.

Conventional methods of applying policy rules to messages in anenterprise network are directed primarily to relatively low-levelmessage protocols such as TCP (transmission control protocol) and IP(Internet protocol). The protocols just described, however, typicallyare implemented at the higher levels of the TCP/IP protocol stack, asrepresented in the International Organization for Standardization (ISO)model. Often, in the interest of speed and finality, firewall servers,for example, are not very effective against message protocols thatinvolve higher levels in the ISO model, or against message protocolsthat are relatively new to the enterprise network and therefore notanticipated by the firewall server. Moreover, many such protocols arebeing rapidly developed and modified, often more quickly than it isfeasible to deploy new systems and methods for recognizing andintercepting those message protocols, and for enforcing policy rulesthereto.

SUMMARY OF THE INVENTION

A protocol management system is capable of detecting certain messageprotocols and applying policy rules to the detected message protocolsthat prevent intrusion, or abuse, of a network's resources. In oneaspect, a protocol message gateway is configured to apply policy rulesto high level message protocols, such as those that reside at layer 7 ofthe ISO protocol stack.

In another aspect, the protocol management system is configured tointercept messages flowing into and out of the network and inspect themessage protocol associated with the messages. If the message protocolmatches a defined protocol template, then the message is forced to usethe protocol message gateway so that policy rules for the messageprotocol can be applied.

In another aspect, the destination of a message heading out of thenetwork to an external server, where the external server is configuredto redirect the message to the destination, can be determined. If it isdetermined that the destination is within the network, then the messagecan simply be redirected to the destination.

These and other features, aspects, and embodiments of the invention aredescribed below in the section entitled “Detailed Description of thePreferred Embodiments.”

BRIEF DESCRIPTION OF THE DRAWINGS

Features, aspects, and embodiments of the inventions are described inconjunction with the attached drawings, in which:

FIG. 1 depicts an exemplary embodiment of an enterprise networkconfigured to incorporate a protocol management system;

FIG. 2 shows a block diagram of a system including a proxy enforcer;

FIG. 3 shows a process flow diagram of a method including proxyenforcement;

FIG. 4 shows a block diagram of a gateway capable of protection againstprotocols of interest;

FIG. 5 shows a process flow diagram of a method of operating a gatewaycapable of protection against protocols of interest;

FIG. 6 shows a block diagram of the deployment of a protocol messagegateway using the CVP method;

FIG. 7 shows a block diagram illustrating the deployment of a protocolmessage gateway using the gateway proxy method;

FIG. 8 shows a block diagram illustrating the deployment of a protocolmessage gateway using the DNS redirect method where only an externalnameserver is used;

FIG. 9 shows a block diagram illustrating the deployment of a protocolmessage gateway using the DNS redirect method where an internalnameserver is used by all client devices inside an enterprise network;

FIG. 10 shows a block diagram illustrating the deployment of a protocolmessage gateway using an HTTP tunnel method;

FIG. 11 shows a block diagram illustrating the deployment of a protocolmessage gateway using the ISA application filter method;

FIG. 12 shows a block diagram of a local server capable of associatingscreen names with users of protocols of interest;

FIG. 13 shows a process flow diagram of a method including associatingscreen names with users of protocols of interest;

FIG. 14 shows a process flow diagram of a method for communicating usinga privacy tunnel.

FIG. 15 shows a block diagram illustrating a message protocol gatewayconfigured to detect user presence; and

FIG. 16 shows a process flow diagram of a method for detecting userpreference.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

FIG. 1 depicts an exemplary embodiment of an enterprise network 110configured to interface with a protocol management system 100 inaccordance with the systems and methods described herein. In the exampleof FIG. 1, enterprise network 110 is coupled to an external network 130through a firewall 120. Enterprise network 110 can be coupled to atleast one local client 170, configured to provide a user 172 access toenterprise network 110. In alternate embodiments, a proxy server (notshown) can be used in place of a firewall 120 to couple external network130 to enterprise network 110.

As can be seen in FIG. 1, system 100 can comprise a protocol messagegateway 122, a proxy enforcer 150, and an authentication module 160.Embodiments, deployments, and applications of protocol message gateway122, proxy enforcer 150, and authentication module 160 are describedbelow in greater detail.

As described herein, enterprise network 110 can include one or moreinternal networks such as a LAN (local area network), WAN (wide areanetwork), locally switched network, or public switched network, someother communication technique, or some combination thereof, by whichdevices locally coupled to enterprise network 110 can communicate witheach other. Although one embodiment is described herein in whichenterprise network 110 includes a LAN, there is no particularrequirement that enterprise network 110 include a LAN, or that anyparticular network configuration be employed.

External network 130 can include the Internet; however, in otherembodiments external network 130 can also include an intranet, extranet,virtual private network (VPN), LAN, WAN, locally switched network orpublic switched network, some other communication technique, or somecombination thereof. Although an embodiment is described herein whereexternal network 130 including the Internet, there is no particularrequirement that external network 130 use the Internet or any otherspecific type of network.

Firewall 120 can include a conventional device for recognizing andintercepting messages formatted at selected levels of the ISO layeredprotocol model, and meeting selected filtering criteria by whichfirewall 120 might determine whether those messages carry informationintended to be received in a certain message protocol format.

In one embodiment of system 100, protocol message gateway 120, proxyenforcer 150, and authentication module 160 can be coupled to anadministration console 180 that can be configured for use by a systemadministrator to set parameters and polices regarding certain protocolsthat are defined to be targets of system 100.

In addition, protocol message gateway 122, and proxy enforcer 150 incertain embodiments, can be coupled to a corporate database 125, whichcan be used to associate user screen names, or aliases, with a specificuser within enterprise network 110. Protocol message gateway 120, andproxy enforcer 150, in certain embodiments, can also be coupled to alogging and archiving subsystem that comprises a data transport service190. Data transport service 190 can be configured to convert protocolmessage logs into a relational model for reporting and, to record thelogs into a report database 196 from which a report 198 can begenerated. In certain other embodiments, such a report can even beconverted to electronic mail that can be mailed to an administrator 192or archived by an electronic mail archive service 194.

FIG. 2 is a block diagram illustrating a communication system 200 thatincludes a proxy enforcer 250 that is described in more detail. System200 also includes an enterprise network 210, a firewall 220, an externalnetwork 230, a protocol message gateway 240, a proxy enforcer 250, and aset of client devices 260.

As will be explained below, protocol message gateway 240 can beconfigured to recognize messages that are using certain target protocolsand implement policy rules associated with the target protocols. Thesetarget protocols can be high level, e.g., ISO level 7, protocols thatwould otherwise often escape detection while entering and exitingenterprise network 210. For example, these message protocols can oftenfind un-monitored communication connections into and out of enterprisenetwork 210, allowing the messages to escape detection. Proxy enforcer250 can, however, be configured to intercept all messages traveling intoand out of enterprise network 210 and force them to pass through definedcommunication connections, e.g., defined ports on protocol messagegateway 240. This way, proxy enforcer 250 can ensure that all messagesflowing into and out of enterprise network 210 are handled by protocolmessage gateway 240, as required, so that the appropriate protocol rulecan be applied to the messages.

Thus, in one embodiment, proxy enforcer 250 can be coupled to firewall220 and disposed so as to be able to passively listen to messages,including individual packets, flowing through firewall 220 into or outof enterprise network 210. Proxy enforcer 250 can include a set ofenforcement rules 252 that are based on a set of protocol definitionfiles 254. Each protocol definition file 254 can be a piece ofexecutable code with intelligent heuristics that can recognize targetprotocols and manage state across multiple connections. For example,there can be an individual definition file 254 for every class orsubtype of target protocol. An individual protocol definition file 254can be different from other protocol definition files 254. Moreover, theset of enforcement rules 252 and protocol definitions files 254 can beexpanded as necessary in response to different target protocols anddifferent ways of handling target protocols. In one embodiment,additional enforcement rules 252 and protocol definition files 254 canbe downloaded from a server interfaced with enterprise network 210.Thus, a system administrator, for example, can define new enforcementrules 252 and/or protocol definitions 254 and update proxy enforcer 250as required.

The protocol definition files 254 act as a protocol template. Proxyenforcer 250 can be configured, therefore, to intercept messages inenterprise network 210 and to then compare them to the protocol templateas defined by the protocol definition files 254. If a match occurs,proxy enforcer 290 can be configured to then implement the correspondingenforcement rule, or rules, 252. Unlike traditional virus recognitionsoftware that relies entirely upon matching patterns, proxy enforcer 250can correlate two different messages or two different blocks within thesame message, such as when a target protocol uses multiple ports and/orstreams. This can be accomplished, for example, because even protocoldefinition file 254 can be configured to create its own data structuresand tables to store information relating to other ports, packets, anddata streams.

A protocol definition file 254 can be configured to identify a targetprotocol in terms of a source IP address for the message; a destinationIP address for the message; a port number associated with the message; aheader string or other set of data values embedded in the message; orsome combination thereof. Proxy enforcer 250 can also be configured todetect protocols of interest in response to a persistent statemaintained by the proxy enforcer 250 in response to sequences ofmessages.

In operation, a remote server 280 coupled to external network 230 andcan be configured to send and receive messages using a target protocolto and from client devices 260. For example, remote server 280 can beconfigured to communicate IM messages with a client device 260.

Proxy enforcer 250 can be configured to then passively listen tomessages as they flow, e.g., through firewall 220. Proxy enforcer 250can comprise a set of proxy enforcement rules 252, e.g., maintained inan enforcement rules database 256. When proxy enforcer 250 intercepts anIM message, i.e., a message that uses a target protocol, proxy enforcerwill match the IM message using the proxy definition files 254. Proxyenforcer 250 can then execute the associated enforcement rule 252. Theenforcement rule 252 can be configured to override aspects of the IMprotocol associated with the intercepted IM message. For example, proxyenforcement rules 252 can require that IM messages pass through theprotocol message gateway 240, which can be configured to act as a proxyfor all IM messages.

Proxy enforcer 250 can be configured to then prevent the message frombeing effective if it does not adhere to proxy enforcement rules 252.One way proxy enforcer 250 can prevent a message 270 from beingeffective is to kill the communication connection between the service ofthe message and the destination, whether or not the message originatesin enterprise network 210 or in external network 230. In alternativeembodiments, proxy enforcer 250 can be configured to reset thecommunication connection associated with the message. In otherembodiments, enforcement rule 252 can cause proxy enforcer 250 to recordinformation related to the message. The recorded information can then beused to generate logs and/or reports as described below.

FIG. 3 is a flow chart illustrating an example method for managingcommunication traffic in a network, such as enterprise network 210,using a proxy enforcer, such as proxy enforcer 250. First, in step 302,proxy enforcer 250 can be configured to passively listen to the messagescomprising the communication traffic. Then, in step 304, proxy enforcer250 can intercept a message and inspect the protocol associated with themessage in step 306. Inspecting the message in step 306 can comprisedetermining information, such as a source IP address, a destination IPaddress, a port number, and a set of text associated with the message.In step 306, proxy enforcer 250 determines if the protocol matches atarget protocol template, e.g., based on the information determined instep 306. The template can, as described above, be defined by one ormore protocol definition files 254. If there is a match in step 303,then proxy enforcer 250 can be configured to execute the associatedenforcement rule 252. If there is no match, then proxy enforcer 250 canbe configured to continue passively listening (step 302).

Protocol definition files 254 can define a pattern of values associatedwith a message that uses a target protocol. Thus, proxy enforcer 250 canbe configured to match (step 303) a pattern of values with datamaintained in a message traffic database 258. Possible examples, e.g.,include matching all traffic on port 5190, all traffic on port 8080 andincluding the string “?ymessage=”, all traffic on port 8080 andincluding a string “?pword=%1”, where, e.g., %1 is a value maintained inthe message traffic database 258, and all traffic on 5190 that includesa string of five characters in incoming packet header, where the fivecharacters as are, e.g., a signature of an instant message used in an IMprotocol.

In certain embodiments, depending upon the type of enforcement rule 252and type of match, further analysis of a message can be performed. Thisis particularly useful, for example, if the initial analysis suggeststhat the message is an IM masquerading as HTTP traffic.

In step 310, the proxy enforcer 250 performs the action associated withone of a plurality of triggered enforcement rules 252. In oneembodiment, only the action associated with the first triggeredenforcement rule 252 is performed; however, in alternative embodiments,more than one action may be performed, with the order of performancebeing responsive to an order in which enforcement rules 252 aremaintained in enforcement rule database 256.

In certain embodiments, enforcement rules 252 include specific actionsto take regarding the intercepted message, including possibly recordingvalues in message traffic database 258. As explained above, possibleexamples of actions to be taken in response to enforcement rules 252include killing the connection associated with the message, resettingthe socket connections, recording the value %1 in message trafficdatabase 258, where %1 is found in the string “?pword=%1” when matchedand/or store the value %1 in a log so that the value can be recognizedin the future, and parsing out the message text and storing the messagesin a log associated with one or more individual users so that themessages and message text can be reviewed at a future point in time.This can be used, for example, to generate a record of unauthorized usesof a network, such as, employees downloading music files.

Thus, proxy enforcer 250, or similarly proxy enforcer 150, can beconfigured to ensure messages that use a target protocol pass throughprotocol message gateway 122. As can be seen in FIG. 1, firewall 120 canalso include memory 126 configured to store a set of recognitionpatterns 124, which can also be referred to as “inspect scripts.”Recognition patterns 124 can, for example, be selected by anadministrator of firewall 120 and can include information sufficient todescribe to firewall 120 messages using a target protocol.

Firewall 120 can be configured to then redirect, in response torecognition patterns 124, at least some of the messages it processes toprotocol message gateway 122. In one embodiment, for example, messagescan be redirected using a conventional content vectoring protocol (CVP)technique, in which, after processing the message and determining thatit should be further processed by protocol message gateway 122, firewall120 delivers the message to protocol message gateway 120. Redirectionusing CVP is described in more detail in conjunction with FIG. 6. Onceprotocol message gateway 122 receives a message, it can ensure thatpolicy rules for the target protocol are employed to handle the message.

FIG. 4 is a diagram illustrating one embodiment of protocol messagegateway 122 in more detail. As can be seen, protocol message gateway 122can include a protocol message parser 410, a gateway manager 420, a setof protocol adapters 430, a policy enforcement module 440, anauthentication module 450, and a set of additional module adapters 460.

In one embodiment, protocol message parser 410 is coupled to firewall120 using a conventional CVP technique, as described above. Protocolmessage parser 410 can thus receive a target message from firewall 120.Protocol message parser 410 parses the received message and determineswhich of the set of protocol adapters 430 is appropriate for processingthe received message. Protocol message parser can be configured to thenforward the message to gateway manager 420. In certain embodiments,protocol message gateway 122 can include more than one protocol messageparser 410. Inclusion of a plurality of protocol message parsers allowsfor relatively easy and efficient scaling of the ability for protocolmessage gateway 122 to receive large numbers of target messages, and toboth parse and distribute those messages-to gateway manager 420 withoutsubstantial degradation in either accuracy or response time.

Gateway manager 420 receives the parsed message and creates anynecessary data structures 422 associated with the message. Among thesedata structures 422, gateway manager 420 can be configured to create anew message event 404, which it can publish to protocol adapters 430 andmodule adapters 460 that indicate an interest in receiving message event404. When publishing message event 404, gateway manager 420 can includeinformation relevant to the parsed message, such as the appropriateprotocol adapter 430 to handle the message, and any other identifyinginformation regarding the message, such as a user, user name, screenname associated with the message, etc.

In one embodiment, gateway manager 420 determines which protocol adapter430 is the appropriate one to handle the message. The appropriateprotocol adapter 430 can then receive the message and its associatedmessage event 404, and can determine how the message fits into theprocessing paradigm for the associated message protocol. For example, ifthe message initiates a session between a sender and receiver, such as asender and receiver of an IM message, protocol adapter 430 can determinethat a new session should be created, and generate a new session event406. In this example, data structures 422 generated and used by thegateway manager 420 would include a session data structure as part ofdata structures 422; the session data structure would includeinformation relevant to the communication session between a sendingclient device 170 and a receiving client device using the associatedmessage protocol.

Protocol adapter 430 assigned to handle the message can be configured tosend any new events 406 it generates to gateway manager 420 forpublishing to any protocol adapters 430 or module adapters 460 that haveindicated interest in that particular message or message event 406.

Inclusion of more than one protocol adapter 430 in protocol messagegateway 122 allows for relatively easy and efficient scaling of protocolmessage gateway 122 to receive large numbers of messages, and toindividually process those messages within protocol message gateway 122without substantial degradation in either accuracy or response time.Further, the use of multiple protocol adapters 430, each specificallydesigned for a different variant of a set of similar target protocols,allows client devices 170 to communicate using the different variants,without any need for special translation on the part of protocol messagegateway 122 and without any need for alteration of client devices 170.

Again, gateway manager 420 can be configured to publish any messageevents 406 to any protocol adapters 430 or module adapters 460 thatindicate interest the message events 406. Among the protocol adapters430 or module adapters 460 that can indicate interest are, for example,policy enforcement module 440, authentication module 450, and selectedother additional module adapters 460.

Authentication module 450 can be configured to receive any sessionevents 406 so that authentication module 450 can authenticate any screennames associated with the associated message. As described in moredetail below, authentication module 450 can be configured to uniquelyidentify an actual user associated with any such screen name, recordthat identifying information in a user database 454 associated withauthentication module 450, and send that identifying information togateway manager 420 for inclusion in any data structure 422 maintainedby gateway manager 420 for the session event 406.

Protocol message gateway 122 can also include a logging module 470 thatcan be configured to provide capability for logging messages as they arereceived by protocol message gateway 122 from a sending client device170, and as they are forwarded by protocol message gateway 122 toreceiving client device 170, or to a client device on external network130. In other words, logging module 470 provides a capability formaintaining a persistent log of all messages exchanged across protocolmessage gateway 122. In one embodiment, logging module 470 can beconfigured to output a log to a logging database 474 from which databasesearches can be conducted and reports generated. In another embodiment,logging module 470 can be configured to output log information tologging database 474 in an encrypted format, so as to restrict access toinformation in logging database 474 to those devices 170 associated withlogging module 470, or possibly those devices 170 associated withgateway 122, that have been assigned access to logging database 474.Access can, depending on the embodiment, be assigned using appropriatekeys for the encrypted format used to encrypt the information.

Logging module 470 provides a way to record messages comprising what isotherwise evanescent communication between sending client devices 170and receiving client devices. Such persistent recording allows forforensic investigation of communication between those client devices.Similarly, such persistent recording also allows for compliance with anyregulatory requirements or other administrative rules requiringmaintenance of records of communications between such client devices.For example, a sending client device 170 and a receiving client devicemay be controlled by users in disparate departments of a financialinstitution. Regulatory requirements can demand that communicationsbetween such users avoid certain topics, such as communication regardinganalysis or recommendation of selected securities. Logging suchcommunications can help ensure that any such requirements are adheredto.

Protocol message gateway 122 can, depending on the embodiment, alsoinclude a policy enforcement module 440. Policy enforcement module 440can be configured to receive information regarding each message, and todetermine whether or not a specific message should be forwarded inunaltered form from sending client device 170. Policy enforcement module440 can have access to a policy rules database 444 that includesspecific policy rules responsive to at least one of certain classes ofinformation including: the nature of sending client device 170; thenature of the receiving client device; the nature of the message; anyinformation, including keywords, included within the message; the day ofthe week, or a time of day, at which the message was sent or is intendedto be received; the size of the message, including whether or not themessage includes an attachment, an executable file attachment, anexecutable file attachment including a virus, and the like; the amountof traffic already sent by sending client device 170, or alreadyreceived by the receiving client device, within a selected duration oftime; or any other classes of information deemed relevant byadministrators of enterprise network 110.

In certain embodiments, protocol message gateway 122 can beadministrated from one or more logically remote administrator consoles180, which can be coupled to enterprise network 110, to another networkthat is coupled to external network 130, or to external network 130itself. The use of remote administrator consoles 180 can allow variousmodules and adaptors included in protocol message gateway 122 to bedynamically updated from a remote location. For example, dynamic policyrules database 444 can be dynamically altered from a administratorconsole 180 in substantially real-time, which can allow real-timeupdates concerning target protocols. Given how quickly dangerous, orharmful, protocols can pop up, and the need to deal with such protocolsas quickly as possible, such dynamic update capability can beinvaluable. Further, the fact that dynamic updates can be performedremotely, even through external network 130, can be even more invaluablesince network administrators cannot always be present to protect theirenterprise networks 110.

FIG. 5 is a flow chart illustrating an example method whereby a protocolmessage gateway 122 can manage communication traffic in a network, suchas enterprise network 110. First, in step 502, protocol message gateway122 can receive a message and direct the received message to a protocolmessage parser 410, which can be configured to parse the message in step504 and determine which of a set of protocol adapters 430 is appropriatefor processing the message. As part of step 504, protocol message parser410 can be configured to forward the message to a gateway manager 420for further processing.

In step 506, gateway manager 420 can receive the parsed message andcreate any necessary data structures 422 associated with the message. Asnoted above, among these data structures 422, gateway manager 420 can beconfigured to create a new message event 404, which it can publish tothose protocol adapters 430 and those module adapters 460 that haveindicated interest in receiving message event 404. As noted furtherabove, when publishing message event 404, gateway manager 420 caninclude information relevant to the message, such as the appropriateprotocol adapter 430 to handle the message, and any other identifyinginformation regarding the message, such as a user, user name, or screenname associated with the message.

In step 508, at least one protocol adapter 430 recognizes the messageand determines how the message fits into the processing paradigm for anassociated message protocol in step 510. In step 512, the protocoladapter 430 can be configured to generate any new events 406 it deemsappropriate in response to how the message fits into the processingparadigm for the associated protocol. Any such new events 406 generatedby the protocol adapter 430 can then be sent to gateway manager 122 instep 514.

In step 516, gateway manager 122 can publish new events 406 to protocoladapters 430 or any other module adapters that have indicated interestin those classes of events 406.

Authentication module adapter 450 can then receive any new session event406, in step 518, and authenticate any screen name associated with theassociated message.

In step 520, logging module adapter 470 can generate a logging entry forthe message and output a log to a logging database 474 from whichdatabase searches can be conducted and reports can be generated. Asnoted above, logging module adapter 470 can output the log informationfor logging database 474 in an encrypted format.

In step 522, policy enforcement module 440 can receive informationregarding each message, and determine whether or not a specific messageshould be forwarded in unaltered form from sending client device 170 tothe receiving client device. As noted above, policy enforcement module440 can have access to a policy rules database 444, including specificpolicy rules responsive to at least one of, and possibly more than oneof, a number of classes of policy information.

There are several deployment options that can be used when implementinga protocol message gateway 122. For example, FIG. 6 is a block diagramillustrating the deployment of a protocol message gateway 122 using theCVP method discussed above. Thus, firewall 620 can comprise a CVP API610, which can be coupled to protocol message gateway 122. Firewall 620can then be configured to have a CVP interface mechanism through whichan external server can be coupled, which in this case is protocolmessage gateway 122. Firewall 620 can direct messages from, e.g.,communication port 5190 or from communication port 2020, to protocolmessage gateway 122 through the CVP interface mechanism using CVP API610.

Alternatively, FIG. 7 is a block diagram illustrating the deployment ofa protocol message gateway using a gateway proxy method in accordancewith another embodiment of the systems and methods described herein. Inthe example of FIG. 7, protocol message gateway 122 comprises a proxymodule 760. In general, a proxy can be a server, or component of aserver, configured to relay a message comprising any protocol to andfrom a client, such as local client device 770 to a server, such asremote server 780. Proxies can be used to shield a client device 770from intrusion from external network 730. Proxies can also be used as acontrolled portal through a firewall 720 or gateway, such as protocolmessage gateway 122. Thus, a protocol message gateway 122 equipped witha proxy module 760 can be configured to permit protocol message gateway122 to act as a proxy and examine any messages within network 710.

Each client application on each local client device 770 should, however,be configured to use protocol message gateway 122 as a proxy. Withoutsuch configuration, local client device 770 can communicate with remoteserver 780 by traversing enterprise network 710, the firewall 720, andexternal network 730 as shown by path 744. Thus, an uncooperative, oruneducated user could willingly, or unknowingly bypass the protocolmessage gateway 122 and a direct path, such as path 744, to communicatewith remote server 780. To help avoid this possibility, the firewall 720can be configured to block all communications except those originatingfrom proxy 760. Unfortunately, conventional firewalls 720 are notequipped to detect some more elusive protocols such as certain IMprotocols. Accordingly, a proxy enforcer 750 can be used to ensure thatmessages traveling within network 710 use protocol message gateway 122as described above.

Thus, with the unauthorized paths blocked, a user can only connected toremote server 780 via proxy 760 by path 742, as allowed by protocolmessage gateway 122. With all, communication traffic flowing throughproxy module 760 protocol message gateway 122 can monitor all trafficfor target protocols and enforce any policies for said protocols asdescribed above.

For convenience, scripts can be executed on a local client device 770,each time a user logs on. The scripts ensure that all clientapplications running on device 770 have protocol message gateway 122 asa proxy. The scripts give an added convenience to the users in that theydo not have to manually configure their proxies. Moreover, the scriptscan be updated remotely using administrator workstations 120, forexample.

FIG. 8 and FIG. 9 illustrate the deployment of a protocol messagegateway 122 using a domain name service (DNS) redirection technique inaccordance with alternative embodiments of the systems and methodsdescribed herein. Often in communicating over a network a clientcommunicates to a server identified by a hostname. At the inception ofcommunications, the client request a nameserver to resolve the hostname.If found, the nameserver responds with the network address of theserver. In the embodiments of FIGS. 8 and 9, the client is given theaddress for gateway 122 each time the hostname for certain servers isrequested.

FIG. 8 shows a block diagram illustrating a deployment of a protocolmessage gateway using DNS redirection, where only an external nameserver890 is used. External nameserver 890 is connected to external network830. A normal DNS request can then be made through path 840 from aclient device 870 to external nameserver 890. Using either a proxyenforcer 850, or firewall 820, the DNS requests can be blocked and theclient device forced to use protocol message gateway 122 for the DNSrequest as a DNS proxy. If client device 870 requests a suspect hostnamethrough path 842, protocol message gateway 122 can be configured to giveits own address as the corresponding address to that host therebyspoofing client 870 into believing protocol message gateway 122 isremote server 880. Protocol message gateway 122 can then relay messagesto remote server 880 and monitor and regulate communications therewith.If the hostname is not know to be one belonging to a certain server,e.g., a server associated with a target protocol, the gateway 122 make arequest to external nameserver 890 through path 844 and respond toclient device 870 with the response given by external nameserver 890.

FIG. 9 shows a block diagram illustrating the deployment of a protocolmessage gateway using DNS redirection, where an internal nameserver 920is used by all client devices 970 inside an enterprise network 910.Internal nameserver 920 can, for example, be coupled to enterprisenetwork 910. Local client devices 970 can make DNS requests through path950 to resolve the addresses of hostnames of servers. In order to keepthe address list up to date internal 960 can periodically synchronizeover path 942 its address list with an external nameserver 990, which isconnected to external network 930, in what is referred to as a “zonetransfer.” To supplement this, protocol message gateway 122 can supply,via path 940, alternate hostnames to internal nameserver 960 to redirectDNS requests for hostnames of servers associated with target protocols.

FIG. 8 and FIG. 9 are given as exemplary embodiments of systemsdeploying protocol message gateway 122 using DNS redirection method. Inwill be understood, however, that numerous equivalent topologies andnameserver protocols can be used to achieve a redirection through DNSspoofing.

FIG. 10 is a block diagram illustrating the deployment of a protocolmessage gateway 122 using an HTTP tunnel method. The deploymentillustrated in FIG. 10 can be used, for example. When firewall 1020 isconfigured to block all external access to the internet except for HTTP.In such a situation, firewall 1020 can be coupled to a “DemilitarizedZone” (DMZ) host 1010 that can be configured to act as a virtualpresence on an external network 1060, i.e. all access to and fromexternal network 1060 goes through DMZ host 1010. When a local clientdevice 1070 sends a message destined for external network 1060, themessage can be forced to first pass through protocol message gateway122, which can, for example, be configured to perform the functionsdescribed above. The message can then be configured to appear as an HTTPmessage by HTTP tunnel module 1050. This way, for example, the messagecan pass through firewall 1020.

HTTP tunnel module 1050 also can be configured as a standalone module orit can be incorporated into protocol message gateway 122 depending onthe embodiment. If fact, HTTP tunnel module 1050 can reside anywherewith the enterprise network, including within firewall 1020, as long asit is configured to perform the functions described herein.

Once HTTP tunnel module 1050 has formatted the message, it can be passedthrough firewall 1020 to, e.g., a web proxy 1030, which can, forexample, be included as part of DMZ host 1010. Web proxy 1030 can beconfigured to forward the message to a relay 1040, which can beconfigured to undo the HTTP formatting, as required, and forward themessage out to external network 1060.

FIG. 11 is a block diagram illustrating the deployment of a protocolmessage gateway 122 using an ISA application filter method, which issimilar to deployment using a CVP method. Thus, firewall 1120 cancomprise an ISA application filter 1110 which can be configured toforward messages comprising a target protocol to protocol messagegateway 122.

Thus, protocol message gateway 122 configured to adapt and enforcemessage protocols associated with messages within an enterprise network,or within some other local network, can be deployed in a variety of waysincluding those described in the preceding paragraphs. Further, a proxyenforcer, such as proxy enforcer 150, can be deployed within theenterprise network to force messages traveling within the network topass through such protocol message gateway 122. Proxy enforcer 150 canalso be configured to terminate a communication connection when it isunable to force a message to pass through protocol message gateway 122.Alternatively, proxy enforcer 150 can be configured to reset acommunication connection associated with a message that cannot be forcedthrough protocol message gateway 122, to log information associatedwithin messages being forced through protocol message gateway 122,and/or to generate reports related to any messages being forced throughprotocol message gateway 122.

As can be seen in FIG. 1, protocol management system 100 can alsoinclude an authentication module 160. Authentication module 160 can beconfigured to identify the identity of users within enterprise network110 from screen names, or aliases, being used by target protocols forassociated messages being passed into and out of enterprise network 110.For example, IM applications often use a screen name as an alias for auser. Messages generated by the IM application then comprise the screenname. It can be useful when adapting or enforcing policies usingprotocol message gateway 122 to identify the actual user associated witha screen name. Authentication module 160 can be configured to performsuch identifications. Moreover, authentication module 160 can beconfigured to store the identifying information so that it can beretrieved later when handling, e.g., IM messages generated by the sameuser using already identified screen names.

FIG. 12 is a diagram illustrating one embodiment of authenticationmodule 160 configured in accordance with the systems and methodsdescribed herein. As can be seen in the example embodiment of FIG. 12,authentication module 160 can comprise part of a protocol messagegateway 122. Alternatively, authentication module 160 can act as astandalone module separate from protocol message gateway 122 asillustrated in FIG. 1. In such an implementation, authentication module160 can, for example, be loaded onto a separate server, or local clientdevice interfaced with enterprise network 110. Similarly, protocolmessage gateway 122 can comprise the local server 1250 comprising a userdatabase 1252. Again, in alternative embodiments, local server 1250 anduser database 1252 can reside outside of protocol message gateway 122 asrequired by the particular embodiment. User database 1252 can beconfigured to maintain an association between user names and screennames, or aliases, used by target protocols within enterprise network110.

In one embodiment, as described above, protocol message gateway 122 caninclude a session manager 1220, capable of receiving messagesintercepted from client devices 170. Session manager 1220 can beconfigured to parse intercepted messages, and determining the messageprotocol associated therewith. Session manager 1220 can also beconfigured to send the message, or information equivalent thereto, tolocal server 1250, which can be configured to generate a new-sessionevent 1244, indicating the receipt of a message. In certain embodimentsa plurality of local servers 1250 can be included, e.g., each adaptedfor processing of a different type of target protocol.

Session manager 1220 can be configured to then distribute session event1244 to one or more other modules within protocol message gateway 122,such as authentication module 160. Authentication module 160 can beconfigured to receive session event 1244 and send a name-request message1246 to an authorization server 128 and receive a name-response message1242 from authorization server 128.

For example, name-request message 1246 sent by authentication module 160to authorization server 128 can include an IP address for the clientdevice 170 sending the message. The name-response message 1242 sent byauthorization server 128 to authentication module 160 can then include aunique user name associated with the client device 170 sending themessage. Once name-response message 1242 is received, authenticationmodule 160 can be configured to first determine if the sessionassociated with session event 1244 is still active. If it is, thenauthorization module 160 can associate the unique user name with ascreen name associated with the message and store the association inuser database 1252. When subsequent messages are received that comprisethe same screen name, authentication module 160 can simply access theassociation information from user database 1252 in order to identify theactual user sending the message.

A policy enforcement module 1230, protocol adapter 1220, and loggingmodule 1260 can then process the message based on the identification ofthe user. For example, policy enforcement module 1230 can determinewhether to allow the message to be forwarded to its originally intendeddestination based on the identification of the user sending the message.

Multiple screen names can be associated with a single user. Thus, theidentification information stored in user database 1292 can comprise acomplete association of all screen names, or aliases, used by aparticular user.

FIG. 13 is a flow chart illustrating an example method for associatingscreen names with unique user names in accordance with the systems andmethods described herein. First, in step 1302, protocol message gateway122 parse a received message and determine an associated messageprotocol. Then in step 1309, protocol message gateway 122 can forwardthe message to a local server 1250 and, in step 1306, can determinewhether the user sending the message is a local user, i.e., coupled toenterprise network 130. If the sending user is a local user, then, instep 1308, local server 1250 can be configured to generate a sessionevent 1244 in response to the message. If the user in not a local user,then the process can jump to step 1312.

In step 1310, local server 1250 within protocol message gateway 122 candetermine if the user sending the message is known to local server 1250,i.e. is the user name associated with a screen name in the user database1252 maintained by local server 1250? If the user sending a message isknown to local server 1250, then nothing needs to be done and themessage can be handled accordingly in step 1328. If the user sending themessage is not known to local server 1250, then, in step 1312, localserver 1250 can be configured to create a guest session, i.e., a newsession with a new user initiating the session. Then, in step 1314,local server 1250 can be configured to send a message to authorizationserver 128, requesting authorization server 128 obtain a unique username for the user. Again, in one embodiment the message from server 1250to authorization server 128 can include an IP address associated withthe sender of the message.

In step 1316, authorization server 128 can identify a client device 170associated, e.g., with the IP address sent received from local server1250, and can interrogate a registry at that client device 170 todetermine a global user ID (GUID) for the client device 170. Becauseauthorization server 128 can directly interrogates the registry at theclient device 170, the local server 1290 can obtain information uniquelyidentifying users without any requirement for cooperation by thoseusers, and without any requirement for cooperation of client devicesunder control of those users. In cases where an individual user using anIM protocol, for example, has a plurality of screen names, local server1250 can still associate all of those screen names with the unique user.

Next, in step 1319, authorization server 128 can request, from a domaincontroller 132, a unique user name associated with the GUID obtainedabove. Domain controller 132 can be configured to respond by sending theunique user name.

Authorization server 128 can be configured to then send the unique username to local server 1250 in step 1320.

In step 1322, local server 1250 can be configured to check the todetermine if the session associated with the message is still inprogress. If the session is not still in progress, e.g., the session wasdropped by the sender of the message, then the process can conclude. Ifthe session is still in progress, then, in step 1324, local server 1250can record the unique user name, and its association with the screenname, in user database 1252.

Protocol message gateway 122 can be adapted to aggregate its treatmentof messages with actual users, regardless of the screen names thoseactual users select for their communications. Thus, if an individualuser has two separate screen names, the protocol message gateway 122 canstill enforce policy rules with regard to the actual user,notwithstanding that user's separation of his messages into messagescomprising two separate screen names. For example, if a particularpolicy rule restricts users from sending or receiving more than 100 IMmessages each hour, protocol message gateway 122 can still restrict anindividual actual user, operating under any one or more screen names,from sending or receiving more than 100 IM messages each hour for allscreen names combined.

The screen name association information stored in user database 1252 canalso be used to identify when a message generated by a user withinenterprise network 110 is intended for destination that is also withinenterprise network 110. For example, one user 172 within enterprisenetwork 110 can send an IM message to another user 172 within enterprisenetwork 110. In a conventional system, the IM message sent from thefirst user would have to pass out of network 110 through externalnetwork 130 to a remote server configured to determine the destinationof the IM message. The remote server would then forward that message, inthis case, back to the second user within enterprise network 110. Aprotocol message gateway 122 configured in accordance with the systemsand methods described herein, however, can recognize, using a screenname associated with the destination, that the second user is withinenterprise network 110 and simply reflect the message to the second useras opposed to allowing it to exit enterprise network 110 and reach theremote server.

Thus, when protocol message gateway 122 receives a new message it cannot only determine if a screen name associated with the source of themessage has been associated with a unique user name in user database1252. But it can also be configured to determine if a screen nameassociated with the destination of the message has been associated witha unique user name in user database 1252. If the user name associatedwith the source of the message has been associated with the unique username in user database 1252, then the policy enforcement rules of thatmessage can be implemented as described above. If the screen nameassociated with the source of the message has not been associated with aunique user name, then the process described above for associating aunique user name with a screen name can be implemented to generate suchan association, which can then be stored in user database 1252.

Similarly, if the session name associated with the destination of themessage has been associated with a unique user name and user database1252, then protocol message gateway 122 can be configured to simplyreflect the message to a client device 170 associated with the uniqueuser name. In this way, protocol message gateway 122 can prevent themessage from traversing out of enterprise network 110, external network130, to a remote server, and back. Not only can this speedcommunications between users 172 within enterprise network 110, but itcan also avoid any of the problems associated with communicating outsideof enterprise network 110.

If a screen name associated with the destination is not associated witha unique user name in user name database 1252, then a similar processfor associating a screen name with a unique user name can beimplemented; however, in this case authorization server 128 may not beable to make the association, because the destination can still beoutside of enterprise network 110. If such is the case, then the messageis not reflected and whatever policy enforcement rules are in place forthe message can be implemented.

It should be noted that the systems and methods described herein canapply across a plurality of gateways interfaced via external network130, for example. In other words, an enterprise can implement multipleprotocol message gateways, with each gateway 122 having informationrelated to the other gateways 122 and client devices 170 associated.Thus, the association information stored in user database 1252 can, incertain embodiments, comprise information related to users associatedwith another protocol message gateway 122. In this case, when a firstprotocol message gateway 122 determines that a screen name ordestination associated with the received message is associated with aunique user name that is in turn associated with a related protocolmessage gateway 122, the first protocol message gateway 122 can beconfigured to simply forward the message directly to the destination,e.g., though external network 130 and the related protocol messagegateway 122, but still bypassing the remote server.

In another embodiment of the systems and methods described herein,protocol message gateway 122 can be configured to construct a privacytunnel between a local client device 170 and a remote client device. Theprocess of devising a privacy tunnel is somewhat similar to the processof reflecting a message when multiple protocol message gateways areinvolved; however, in this case, the remote client device is notnecessarily associated with a protocol message gateway that is in turnassociated with protocol message gateway 122. Protocol message gateway122 does however need to know information related to the remote clientdevice and/or a protocol message gateway associated therewith. When alocal client device 170 generates a message intended for the remoteclient device, protocol message gateway 122 can be configured to set upa direct communication link with the remote client device and/or itsassociated protocol message gateway. In other words, a remote, or local,server can be bypassed when protocol message gateway 122 recognizes thatthe message generated by local client device 170 is intended for aremote client device about which it possesses direct connectioninformation. Moreover, the communication link between the local clientdevice 170 and the remote client device can be made secure even whencommunication via a remote server would not be.

A flow chart illustrating an exemplary embodiment for generating aprivacy tunnel in accordance with the systems and methods describedherein is illustrated in FIG. 14. First, in step 1402, a local user, ora remote user, can invoke a secure communications session by submittinga signal to protocol message gateway 122. In one implementation, theuser invokes a secure session by transmitting a specified string such as“<SECURE>”. Protocol message gateway 122 observes the request, in step1404, and invokes a secure communications channel by downloading asecure thin client to the remote client device in step 1406. The remoteclient device can then invoke, in step 1408, the thin client. Protocolmessage gateway 122 can then establish a secure communications channelthrough the external network 130 in step 1410.

When protocol client device sends a message to the remote client device,protocol message gateway 122 can intercept the message, in step 1413,and forward it to the thin client running on the remote client device instep 1414.

When either user desires to terminate the secure communication, theirclient device can send a signal indicated to protocol message gateway122 in step 1416. In one embodiment, the termination of the secure suchsession is specified using a string such as “<ENDSECURE>”. Protocolmessage gateway 122 received the request in step 1410 and terminates thesecure communications channel. Upon terminate, the thin clientterminates its execution and the remote client device releases allresources used by the thin client in step 1420. The remote client devicecan then delete the thin client device in step 1422.

In certain embodiments, protocol message gateway 122 can interceptmessages from a local client and translate then from one messageprotocol to another before sending them to the remote client device.This is useful, for example, where the remote client device and localclient device are using different message protocols.

FIG. 15 is a diagram illustrating a message protocol gateway 1500configured to detect and report when users log on to an applicationwithin, e.g., network 110. In the example of FIG. 15, protocol messagegateway 1500 can comprise a message protocol element 1510 and a usagedatabase 1520. Message protocol element 1510 can be configured to sendand receive messages to and from client devices 170, e.g., usingenterprise network 110, or to and from external client devices, e.g.,using enterprise network 110 and external network 130. Messages sent orreceived by message protocol element 1510 can implement various targetprotocols, such as those described above.

Usage database 1520 can include a set of database tables, including auser table 1550 and an inverted user table 1560. Although usage database1520 is described herein with regard to detecting and reporting userpresence it will be apparent that usage database 1520 is capable of verygeneral extension to detecting and reporting the presence or absence ofother resources, and of detecting and reporting other types of events.Usage database 1520 also includes a set of database codes, including aset of SQL instructions 1522 and a set of SQL extensions 1540. It willbe understood, of course, that although usage database 1520 is describedherein with regard to SQL as an individual instance of a databasemanipulation and querying language, usage database 1520 can also beconfigured for other types of database manipulation and querying, and toother types of databases or data sources in general.

In one embodiment, user table 1550 includes a set of entries 1552,sometimes referred to as “rows”, each of which includes information fora selected user 172. In such embodiments, user table 1550 includes a setof fields 1554, sometimes referred to as “columns” for each entry 1552,each of which includes a selected data item, or list of data items, forthe user associated with that entry 1552. For example, user table 1550can include a first field 1554 a that can comprise a user nameassociated with a selected user, a second field 1554 b that can comprisea contact list associated with the selected user, and a third field 1554c that can comprise an online/offline status associated with theselected user.

Field 1554 b can, depending on the embodiment, comprise amultidimensional column, i.e., the value associated with field 1554 canitself be a list. SQL extensions 1540 include functions capable ofgenerating a list, e.g., of multiple rows from a multidimensional column1554, and functions capable of generating a multidimensional column 1554from a list. This has the effect that a database query otherwiseinvolving linking multiple database tables is capable of being performedusing operations on a single database table. For example, without usingmultidimensional columns, associating a contact list with a selecteduser might involve a separate linking table, indicating for each pair ofusers, e.g., user A and user B, whether user B is on user A's contactlist. Thus, conducting a contact list query would involve at least onesearch of the linking table and at least two searches of the user table.By using multidimensional columns, however, associating a contact listwith a selected user involves only a single search of the user tableitself and the use of a SQL extensions 1540 to generate a list from themultidimensional column used for the contact list.

In one embodiment, inverted user table 1560, similar to user table 1550,includes a set of entries 1556, each of which includes information for aselected user 172. Inverted user table 1560, similar to the user table1550, can include a set of fields 1558 for each entry 1556, each ofwhich includes a selected data item, or list of data items, for the userassociated with that entry 1556. In one embodiment, inverted user table1560 includes a first field 1558 a including a user name associated witha selected user, and a second field 1558 b including an inverted contactlist associated with the selected user. The inverted contact listassociated with that selected user in this case can be used to indicatethose other users who have listed the selected user on their contactlists. Accordingly, when a newly logged-in user is detected, it isrelatively easy to search for the set of other users who wish to beinformed of the presence of that newly logged-in user.

In one embodiment, SQL extensions 1540 can also include functionscapable of specifying a set of database queries expected to be performedfrequently, and for which it is desirable to construct an inverted tablein response to the original table, similar to the relationship betweeninverted user table 1560 and user table 1550. In such embodiments, SQLextensions 1540 can, for example, include one or more of the followingfunctions: a function allowing a designer to specify if an invertedtable should be automatically constructed in response to an originaltable, similar to the relationship between inverted user table 1560 anduser table 1550, and if so, how fields 1558 of the inverted table relateto any corresponding fields 1554 of the original table; a functionallowing a designer to specify if a query relating to the original tableshould be translated into a query to be performed relating to theinverted table, and if so, how fields 1558 of the inverted table shouldbe tested in correspondence to any testing of fields 1554 of theoriginal table; a function allowing a designer to specify if a query,relating to either an original table or an inverted table, should haveits results cashed for later use, and if so, upon what triggers shouldthat query and/or later use be performed.

For example, a query relating to which users on contact lists arelogged-in might be performed in response to one or more of the followingtriggers: (1) when a user logs in, (2) when a user logs out, (3) after aselected period of time expires, (4) after protocol message gateway 1500is rebooted or reset, and (5) after a selected number of messages havebeen processed.

SQL extensions 1540 can also include a function allowing a designer tospecify if a query, relating to either an original table or an invertedtable, should be performed and its results calculated before any actualrequests therefore, and if so, upon what triggers should that query beperformed.

SQL extensions 1540 can also include a function allowing a designer tospecify whether a table should include a multidimensional column, and ifso, how that multidimensional column should be treated in response toquery results. For example, a query relating to which users on contactlists are logged-in might include a multidimensional column relating tothe contact list for each user, and upon performance of a query, resultsfrom that multidimensional column might be aggregated and then separatedinto individual row responses for specific users that are one thecontent list of the queried user.

Thus protocol message gateway 1500 can be configured to allow efficient,time saving detection of user's present on network 110 and logged on toan application also being used by the user. This can save processing andother resources within network 110. This functionality can be extendedby allowing, e.g., a network administrator, to define multidimensionalcolumns, and multidimensional column associations, for other types ofdatabases and database searches.

FIG. 16 is a flow chart illustrating an example method for detection andreporting of user presence in accordance with one embodiment of thesystems and methods described herein. First, in step 1602, an internaluser 172 at a client device 170, or an external user at an externalclient device, attempts to login to use an application. In step 1604, anassociated client device 170 can be configured to send a message toprotocol message gateway 122 indicating the attempt to login, andincluding information required to login, e.g., a user name or screenname. In step 1606, protocol message gateway 122 can receive the messageindicating the attempt to login, and can, for example, respond to clientdevice 170 indicating receipt thereof. In step 1608, if protocol messagegateway 122 has sufficient information to verify the login attempt, orto deny the login attempt, then it can be configured to respond toclient device 170 so indicating.

For example, protocol message gateway 122 can be configured to haveavailable cached information from an external server indicating whichinternal users 172 and which external users are presently authorized tologin to use the application. In such an embodiment, use of theapplication can be associated with access to the external server. Thus,the login can actually be an attempt to login to a server, e.g., theexternal server, associated with the application.

In another implementation, protocol message gateway 122 can beconfigured to have available a known procedure by which it can determineif the login message is valid, such as for example by reference to apublic-key cryptosystem or other trusted server.

In step 1610, if the login is successful, then the process can continueto step 1612. If, however, the login is not successful, then protocolmessage gateway 122 can deny the attempt and wait for another message(step 1602). In step 1612, protocol message gateway 122 can beconfigured to perform any SQL instructions 1520 associated with thelogin. SQL instructions 1520 can, for example, call upon a set of SQLextensions 1540, such as, for example, when using multiple dimensionalcolumns.

In one embodiment, a SQL instructions 1520 associated with the loginmessage can include detecting if any other user, whether an internaluser 172 or an external user, on the contact list for the newlylogged-in user, is also logged in. For example, SQL instructions 1520can include a query to be performed against a user table 1550, searchingfor the contact list associated with the newly logged-in user, anddetermining if any users on that contact list are already logged in.Thus, the newly logged-in user can be informed of any associated usersalready logged in.

In another embodiment, SQL instructions 1520 associated with the logincan also include detecting if the newly logged-in user is on any contactlist for any users already logged in. Thus, users already logged in canbe informed of the presence of the newly logged-in user, if that newlylogged-in user were on any contact lists for any users already loggedin.

Accordingly, performing SQL instructions 1520, in step 1612, can directusage database 1520 to search an inverted user table 1560 for a newlylogged-in user. In one embodiment, SQL instructions 1520 associated withthe login calls upon a set of SQL extensions 1540 to search an inverteduser table 1560 for the newly logged-in user. For example, in oneembodiment, the set of users listing the newly logged-in user on theircontact lists can be specified by the SQL extensions 1540 to include amultidimensional column, with the effect that performing the searchprovides a list of such users. In this example, a multidimensionalcolumn can be specified by SQL extensions 1540 to be expanded out to aset of rows, each indicating a single user listing the newly logged-inuser on their contact list. Thus, SQL instructions 1520, or some otherinstruction, can be employed to so inform each of those users of theuser presence of the newly logged-in user. Protocol message gateway 122can be configured to then inform each of the set of users listing thenewly logged-in user on their contact lists of the user's presence.

It should be apparent that similar steps might be performed by protocolmessage gateway 122 in response to other actions having an effect onstatus of user presence including, for examples, when a new user isregistered with protocol message gateway 122, when a user of a selectedtype, such as a system administrator or chat room facilitator changesthe status of their user presence, or when a user logs out.

While certain embodiments of the inventions have been described above,it will be understood that the embodiments described are by way ofexample only. Accordingly, the inventions should not be limited based onthe described embodiments. Rather, the scope of the inventions describedherein should only be limited in light of the claims that follow whentaken in conjunction with the above description and accompanyingdrawings.

1. A method for managing communication traffic in a network, the methodcomprising: intercepting with a gateway module an instant message from asource computing device of a first user intended for an external serverconfigured to redirect the instant message to an intended destinationcomputing device of a second user, wherein the gateway module and thesource computing device are located within an enterprise network and theexternal server is located outside the enterprise network; identifyingthe intended destination computing device based at least in part onidentifying information associated with the second user; determiningwhether the intended destination computing device is within theenterprise network; and in response to determining that the intendeddestination computing device is within the enterprise network,redirecting the intercepted instant message to the intended destinationcomputing device by bypassing the external server such that theintercepted instant message does not exit the enterprise network;wherein at least said redirecting is performed by computer hardware. 2.The method of claim 1, wherein the message comprises an instant message.3. The method of claim 1, further comprising selecting a policy rule forhandling the message and applying the policy rule to the interceptedmessage.
 4. The method of claim 3, wherein the policy rule is based onthe intended destination of the intercepted message.
 5. The method ofclaim 3, wherein the policy rule is based on information included in theintercepted message.
 6. The method of claim 3, where in the policy ruleis based on when the intercepted message is sent or intended to bereceived.
 7. The method of claim 3, wherein the policy rule is based onthe size of the intercepted message.
 8. The method of claim 3, whereinthe policy rule is based on whether the intercepted message includes anattachment.
 9. The method of claim 3, wherein the policy rule is basedon whether the intercepted message includes a virus.
 10. The method ofclaim 3, further comprising determining if a session associated with theintercepted message is still in progress before applying the policyrule.
 11. A system for managing communication traffic in a network, thesystem comprising: a gateway module comprising computer hardware, thegateway module configured to be located within an enterprise network andto intercept a message from a source computing device intended for anexternal server configured to redirect the message to a destinationcomputing device, wherein the external server is located outside theenterprise network, and wherein the gateway module is configured to:identify an intended user recipient of the message based at least inpart on identifying information associated with the user recipient,determine whether the destination computing device is within theenterprise network, and in response to determining that the destinationcomputing device is within the enterprise network, redirect the messageto the destination computing device by at least bypassing the externalserver such that the message does not exit the enterprise network. 12.The system of claim 11, wherein the message comprises an instantmessage.
 13. The system of claim 11, wherein the gateway module isfurther configured to select a policy rule for handling the message andto apply the policy rule to the intercepted message.
 14. The system ofclaim 13, wherein the policy rule is based on the intended destinationof the intercepted message.
 15. The system of claim 13, wherein thepolicy rule is based on information included in the intercepted message.16. The system of claim 13, wherein the policy rule is based on when theintercepted message is sent or intended to be received.
 17. The systemof claim 13, wherein the policy rule is based on the size of theintercepted message.
 18. The system of claim 13, wherein the policy ruleis based on whether the intercepted message includes an attachment. 19.The system of claim 13, wherein the policy rule is based on whether theintercepted message includes a virus.
 20. The system of claim 13,wherein the gateway module is further configured to determine whether asession associated with the intercepted message is still in progressbefore applying the policy rule.